home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
newsgroups
/
misc.20030409-20031118
/
000233_fdc@sesame.cc.columbia.edu_Wed Aug 20 15:51:38 EDT 2003.msg
< prev
next >
Wrap
Text File
|
2020-01-01
|
4KB
|
78 lines
Article: 14471 of comp.protocols.kermit.misc
Path: newsmaster.cc.columbia.edu!news-not-for-mail
From: fdc@sesame.cc.columbia.edu (Frank da Cruz)
Newsgroups: comp.protocols.kermit.misc
Subject: Re: Kermit for PC upgrade/transfer
Date: 20 Aug 2003 15:51:33 -0400
Organization: Columbia University
Lines: 61
Message-ID: <bi0jg5$eod$1@sesame.cc.columbia.edu>
References: <cRN0b.4242$B8.2894@newsread2.news.atl.earthlink.net> <bi0hdj$cqu$5@blue.rahul.net>
NNTP-Posting-Host: sesame.cc.columbia.edu
X-Trace: newsmaster.cc.columbia.edu 1061409093 11194 128.59.59.56 (20 Aug 2003 19:51:33 GMT)
X-Complaints-To: postmaster@columbia.edu
NNTP-Posting-Date: 20 Aug 2003 19:51:33 GMT
Xref: newsmaster.cc.columbia.edu comp.protocols.kermit.misc:14471
In article <bi0hdj$cqu$5@blue.rahul.net>,
<dold@KermitXfor.usenet.us.com> wrote:
: Brad in MI <bNOrSPAMv4inMEc@earthlink.net> wrote:
: > I've gone through the Kermit website (wow, lots of stuff!) and am
: > considering getting Kermit to transfer files to my new PC. I have a
: > couple of questions, though.
:
: > The old PC is Windows 95B, and the new one is Windows XP Pro. Each PC
: > has a 56K modem. Can I connect the two via a simple 6-ft phone line
: > between the two modems for this transfer?
:
: As much as I love Kermit, this really isn't the right application for it.
: For the cost of a Windows95 license, you could buy two NIC cards and a
: crossover cable, and use Windows file sharing to copy all the files.
:
This would probably work, but if it didn't you'd waste lots of time
figuring out what's wrong and fixing it -- drivers, interrupts, etc etc.
: Or you could take the disk out of the old machine and put it in the new
: machine and copy everything.
:
If the old disk and new PC were compatible and if you didn't need the first
machine to be up for some reason.
: Or you could buy a software/hardware product designed for just exactly this
: purpose, that includes a cable (serial, parallel, or USB).
:
Sometimes there are reasons for using Kermit for this:
. You already have Kermit and know how to use it.
. The machines are not colocated (doesn't apply in this case).
. There is a reason that your machine doesn't have a network interface.
etc etc. While Kermit does not have a "Lap-Link" like user interface,
it's perfectly well suited for bulk directory-tree copies from one machine
to another. The Windows-to-Windows case is, of course. "trivial", but
Kermit can do the same thing between Windows and UNIX, UNIX and VMS,
Windows and VMS, etc, so for people who do a lot of this kind of work on
a variety of platforms, Kermit is not an unreasonable choice. It can
descend through directory trees and replicate them (if necessary) on
the receiving end, switch automatically between text and binary mode for
each file, convert record formats and character sets of text files (if
necessary), and allows all kinds of fancy selection criteria and processing
options that might come in handy:
[C:\tmp\] K-95> send ? Filename, or switch, one of the following:
/after: /delete /mail: /print: /smaller-than:
/array: /except: /move-to: /protocol: /starting-at:
/as-name: /filter: /nobackupfiles /quiet /subject:
/before: /filenames: /not-after: /recover /text
/binary /larger-than: /not-before: /recursive /transparent
/command /listfile: /pathnames: /rename-to: /type:
[C:\tmp\] K-95>
Of course I'm partial, but even so... I often find myself using Kermit
to solve some problem that might be better solved with some other tool
because I know how to do it with Kermit. Usually Kermit finishes the job
before I could have gathered the other tools and/or figured out how to
use them.
- Frank